Fixes #56 : Top Level docker-compose by Kmadhav824 · Pull Request #57 · shivamxverma/CodeSM

Kmadhav824 · 2026-04-26T18:24:32Z

I've added a top level docker-compose yaml for devs

vercel · 2026-04-26T18:24:36Z

@Kmadhav824 is attempting to deploy a commit to the Shivam verma's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copilot

Pull request overview

Adds a top-level Docker Compose setup intended to support local development by providing shared infrastructure services, while also updating ignores, cleaning committed logs, and adjusting schema/dependency wiring in the monorepo.

Changes:

Add root docker-compose.yaml with Postgres + Redis services for local dev.
Remove committed log/audit artifacts and expand .gitignore rules across packages to prevent re-adding them.
Update lockfiles/dependencies and adjust backend schema import pathing.

Reviewed changes

Copilot reviewed 7 out of 23 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
`docker-compose.yaml`	Introduces Postgres + Redis services for local development.
`.gitignore`	Expands repo-wide ignores for deps, env files, logs, and build outputs.
`backend/.gitignore`	Adds backend-local ignores for env/logs/scratch/build artifacts.
`workers/.gitignore`	Adds workers-local ignores for deps/env/logs/build artifacts.
`Frontend/.gitignore`	Expands env ignore patterns and adds coverage output ignore.
`backend/src/loaders/postgres.ts`	Changes schema import to a deep relative path to `db-schema/src`.
`workers/pnpm-lock.yaml`	Updates workers dependency graph (incl. BullMQ/Drizzle/PG/Winston entries).
`db-schema/pnpm-lock.yaml`	Updates db-schema lockfile content (removes prior dev dependency entries).
`workers/logs/error/error-2026-04-25.log`	Removes committed runtime log artifact.
`workers/logs/error/error-2026-04-24.log`	Removes committed runtime log artifact.
`workers/logs/error/error-2026-04-23.log`	Removes committed runtime log artifact.
`workers/logs/error/error-2026-04-22.log`	Removes committed runtime log artifact.
`workers/logs/combined/combined-2026-04-25.log`	Removes committed runtime log artifact.
`workers/logs/combined/combined-2026-04-24.log`	Removes committed runtime log artifact.
`workers/logs/combined/combined-2026-04-23.log`	Removes committed runtime log artifact.
`workers/logs/combined/combined-2026-04-22.log`	Removes committed runtime log artifact.
`workers/logs/combined/.a38ab147e6d6cf164f60c30ab92bc91339f28bcb-audit.json`	Removes committed log-rotation audit artifact.
`backend/logs/error/error-2026-04-21.log`	Removes committed runtime log artifact.
`backend/logs/error/error-2026-04-20.log`	Removes committed runtime log artifact.
`backend/logs/error/error-2026-03-31.log`	Removes committed runtime log artifact.
`backend/logs/combined/combined-2026-04-20.log`	Removes committed runtime log artifact.
`backend/logs/combined/.0249dc91aa5f529d3b84500f8c29e94ef13aaf30-audit.json`	Removes committed log-rotation audit artifact.

Files not reviewed (2)

db-schema/pnpm-lock.yaml: Language not supported
workers/pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-26T18:29:08Z

+    command:
+      [
+        "redis-server",
+        "--requirepass",
+        "strong_password_123",
+        "--appendonly",
+        "yes"
+      ]
+    ports:
+      - "6379:6379"
+    volumes:
+      - redis_data:/data
+    healthcheck:
+      test: ["CMD", "redis-cli", "-a", "strong_password_123", "ping"]


The healthcheck embeds the Redis password via redis-cli -a .... If you move the password to an env var, update the healthcheck to reference it too (so the password isn’t duplicated in multiple places).

Suggested change

command:

[

"redis-server",

"--requirepass",

"strong_password_123",

"--appendonly",

"yes"

]

ports:

- "6379:6379"

volumes:

- redis_data:/data

healthcheck:

test: ["CMD", "redis-cli", "-a", "strong_password_123", "ping"]

environment:

REDIS_PASSWORD: strong_password_123

command: >

sh -c 'exec redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes'

ports:

- "6379:6379"

volumes:

- redis_data:/data

healthcheck:

test: ["CMD-SHELL", "redis-cli -a \"$$REDIS_PASSWORD\" ping"]

Copilot · 2026-04-26T18:29:08Z

 import { drizzle } from 'drizzle-orm/node-postgres';
 import logger from './logger';
-import { schema } from 'db-schema';
+import { schema } from '../../../db-schema/src/index';


Importing the schema via a deep relative path (../../../db-schema/src/index) tightly couples backend to the monorepo folder layout and bypasses the existing TS path mapping for db-schema (see backend/tsconfig.json paths). Prefer importing from db-schema and fixing the package to export/build the intended entrypoint (e.g., ensure ../db-schema/dist exists or adjust db-schema exports/paths).

Suggested change

import { schema } from '../../../db-schema/src/index';

import { schema } from 'db-schema';

Copilot · 2026-04-26T18:29:08Z

+services:
+  postgres:
+    image: postgres:17-alpine


The PR description says this only adds a top-level docker-compose for devs, but the diff also includes dependency/lockfile changes (e.g., workers/db-schema pnpm-lock updates) and a backend code change (schema import). If these are intentional, it would help to call them out in the PR description or split them into separate PRs so the docker-compose change can be reviewed/rolled back independently.

Copilot · 2026-04-26T18:29:08Z

+    environment:
+      POSTGRES_DB: codesm_dev
+      POSTGRES_USER: codesm
+      POSTGRES_PASSWORD: codesm_dev_password
+    ports:


The compose file hard-codes PostgreSQL credentials in-repo. Even for dev, this makes it easy to accidentally reuse weak/shared secrets and encourages committing credentials. Consider moving these values to an .env/env_file (with a checked-in .env.example) and referencing them via ${...} in the compose file.

Copilot · 2026-04-26T18:29:09Z

+    command:
+      [
+        "redis-server",
+        "--requirepass",
+        "strong_password_123",
+        "--appendonly",
+        "yes"
+      ]


The Redis password is hard-coded in the compose file (--requirepass ...). This is easy to leak and makes rotation awkward. Prefer sourcing it from an .env/env_file and using variable substitution so each dev can set their own value.

Kmadhav824 added 2 commits April 26, 2026 23:40

Added yaml for starting up tools for local development

9a6f584

Updated gitignore for neglecting logs and stale artifacts

7bc78d4

Copilot AI review requested due to automatic review settings April 26, 2026 18:24

Copilot started reviewing on behalf of Kmadhav824 April 26, 2026 18:24 View session

Copilot AI reviewed Apr 26, 2026

View reviewed changes

Kmadhav824 changed the title ~~Fixes #56 : Top Level docke-compose~~ Fixes #56 : Top Level docker-compose Apr 26, 2026

Kmadhav824 added 2 commits April 27, 2026 02:57

Added Migration Scripts

8e409f0

Corrected schema path across services, packages updated, readme changes

04ff2f3

Kmadhav824 merged commit f4fcbbb into shivamxverma:main Apr 26, 2026
2 of 3 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fixes #56 : Top Level docker-compose#57

Fixes #56 : Top Level docker-compose#57
Kmadhav824 merged 4 commits intoshivamxverma:mainfrom
Kmadhav824:main

Kmadhav824 commented Apr 26, 2026

Uh oh!

vercel Bot commented Apr 26, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 26, 2026

Uh oh!

Copilot AI Apr 26, 2026

Uh oh!

Copilot AI Apr 26, 2026

Uh oh!

Copilot AI Apr 26, 2026

Uh oh!

Copilot AI Apr 26, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	import { schema } from '../../../db-schema/src/index';
	import { schema } from 'db-schema';

Conversation

Kmadhav824 commented Apr 26, 2026

Uh oh!

vercel Bot commented Apr 26, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 26, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants